🐛 Issue

We are running into unresolvable issues on Liquid, and want to support path based routing for better SEO optimization

✏️ Solution

1. Abstract all navigation actions into a navigation hook.
2. Inside that navigation hook, navigate using alternative strategies depending on the current type of auth enabled
3. Abstract out the current "id" so it can come from a variety of sources - params, feed id, or content id
   • Right now we have two paths /ac/ and /af/. Technically both are identical, but may come in handy as we continue to iterate on our routing strategy.
4. Ditch breadcrumbs

🔬 To Test

in the web-embeds site

1. Click around the app.
2. Navigation will happen via path
3. Now change data-use-path-router="true" to data-use-path-router="false" in the index.html
4. Navigate around the app
5. Navigation will happen via params.

📸 Screenshots